S3Drive - Cubbit - Special characters 403

Aloha, I am using the S3Drive App on Android (v1.7.6). The error is currently happening for some files of various filetypes consistently. In this example I used a pdf. I can access other pdf files without a problem. I am connected to my s3 provider cubbit.io. Over the webpage of the provider I can access the files without a problem.

Hi @Philipp, coincidentally we've improved character encoding for Cubbit in version 1.7.7 based on some user reports: https://s3drive.app/changelog Please update to 1.7.7 and let me know if problem still persist. The issue was caused by the: ( and ) and $ characters only for buckets where versioning was disabled. If you still face this problem even after updating the S3Drive, please send me the full filepath (including special characters - feel free to redact standard alphanumerics for privacy), bucket name and settings (versioning, object lock etc.). (edited)

Tom changed the channel name: Cubbit - Encountering 403 1/28/2024 10:55 PM

The fix works on my machine

No error when I open the files. Thanks for the quick answer and your great work. I will cosider purchasing the app

Hi, I would like to reopen this. I found another one. The app version I am using is 1.8.0 The name of the file is: Guy Haley - Dawn of Fire, Book 1 - Avenging Son path to file: \Archiv\Audiobook\Warhammer\W40k\Space Marines\Dawn of Fire - Indomitus Crusade\Guy Haley - Dawn of Fire, Book 1 - Avenging Son I get the identical error (edited)

Based on your filepath provided we'll try to reproduce the issue and squeeze the fix in a next release.

Hi @Philipp, we can't really reproduce that one. Based on delimiter, is it Windows? Are you happy to remove special characters or any whitespaces from the filename or/and path and see if it helps? Would you be happy to make to move the source file to different location (e.g. with less directory nesting) and see if it helps? As long as we manage to figure out how which character is at fault we can then provide a hotfix. Thanks

Hi, I think it was the comma. (edited)

8:30 PM

I only had the error when there was a comma in it

8:31 PM

To your question I opened the file in the mobile app.

8:31 PM

renaming was fine but not downloading

Hi @Philipp, We've have found that if Cubbit bucket isn't versioned then indeed comma character causes some issues. We've added a quick fix which encodes command and will end up in a next release.

Tom changed the channel name: Cubbit - Special characters 403 4/16/2024 8:23 AM

yes we can configure that at Cubbit. Didn't know this could cause this. I will consider this next time I write a error report here. I will share how I configure the bucket next time.